home *** CD-ROM | disk | FTP | other *** search
- Path: news.iadfw.net!usenet
- From: Mark Nelson <markn@airmail.net>
- Newsgroups: comp.lang.c++
- Subject: Re: Help w/ C++ DLLs and VBasic
- Date: Wed, 10 Apr 1996 20:23:37 -0500
- Organization: Guest user
- Message-ID: <316C5F19.4ABE@airmail.net>
- References: <4k1kv1$181o@hearst.cac.psu.edu>
- NNTP-Posting-Host: dal07-17.ppp.iadfw.net
- Mime-Version: 1.0
- Content-Type: text/plain; charset=us-ascii
- Content-Transfer-Encoding: 7bit
- X-Mailer: Mozilla 2.0GoldB2 (Win95; I)
-
- rdg@falcon.arl.psu.edu wrote:
- >
- > Does anyone have any advice on what I may be omitting in the DLL that is
- > causing the function not to appear in the DLL interface (at least as far
- > as VB is concerned). I have also looked at the DLL with the DOS
- > "dumpbin/exports" utility and it shows that the functions have been
- > listed as exported from the DLL.
-
- Microsoft made this difficult, but they do offer some help. Your VB40
- root directory has a text document describing the hoops you need to jump
- through in order to talk to C++ DLLs from VB.
-
- My personal solution unfortunately had to fall back on using a DEF file
- instead of the inline declspec() notation. If you use the declspec()
- and don't supply a def file, then you are going to have to supply a
- mangled alias name for your function in your BAS declaration. That's
- because VC++ 4.0 decided to start mangling the names of exported functions
- declared with the _stdcall convention.
-
- Mark Nelson
- http://web2.airmail.net/markn
-